After running Windows 7 for a week or so now, I've found it very similar to Vista in more ways than one. While being undeniably prettier than even Vista was, and with more easily accessible system options and functions, I still see a very big problem in the networking area. This operation system, as with Vista, has not been designed to easily and seamlessly work with computers running any older versions of Microsoft's operating systems. As all Windows operating systems come from the same company, there is no excuse why new versions of Windows should not be easy and simple to network to existing computers that are forced to run older versions of Windows due to hardware restrictions. For example, I had the beta version of Windows 7 running on a quad core, Vista Ultimate running on a dual-core, XP on an Inspiron 4150, and 2000 Server on a Compaq ML370 G2 server. They are all running off a router for internet connection, but none of them can see anything from the other, be it be a local printer, shared network drive, or even a simple shared folder. For this reason, after a week, I have reverted to running XP on all three personal computers, and 2000 on the server. Most networks are not going to consist of only computers that are able to run the latest version of Windows, and being as companies and private customers are not in the position nowadays to replace every computer in their network, this version is going to succeed as well as Vista did. True, a few pre-built systems with an OEM license will sell, but thoes of us that purchase multiple licenses from Microsoft will not be interested in W7 as we need to continue to be able to allow all the computers in our networks to continue to operate together without making any major hardware changes to the computers already running. I for one will continue to purchase XP licenses for each computer I build, until the operating system is released that does not put restrictions on what computer it will or will not allow to share a network with. So basically, come on Microsoft, release a new operating system that is as easy to network to any other version as it is to network two XP systems.

I do find it strange how the sort of person who cannot be bothered to read through the other networking threads for a solution to see how easy it actually is to set up a network insists of telling MS that networking is awful. It find it even more absurd that you say networking is difficult even tho if you know what you are doing it is easily setup. People do not seem willing to adapt to change, and well, from MS perspective, I imagine their answer will simply be 'well, you cant please everybody'.

Will01 said:I do find it strange how the sort of person who cannot be bothered to read through the other networking threads for a solution to see how easy it actually is to set up a network insists of telling MS that networking is awful. It find it even more absurd that you say networking is difficult even tho if you know what you are doing it is easily setup. People do not seem willing to adapt to change, and well, from MS perspective, I imagine their answer will simply be 'well, you cant please everybody'. Perhaps that sort of person is trying to test network behaviour from 'vanilla' Windows installations. After all, the average user isn't going to figure this out all by himself or by browsing the Microsoft TechNet Forums.Microsoft has always promised seamless integration of network capabilities and I agree with the OP that they should deliver for a change. Obviously any power user could get this to work across all the platforms, but that's besides the point.

Unlike Vista, I was able to get my shares up and running right away after W7 install.I was able to set my workgroup name and see my other machines (all XP SP3), and shares right away.I did ask for a user name & pass with permissions on each machine, which is to be expected.The behavior of the discovery leads me to believe that W2K should not be a problem.I am going to try a Linux box shortly and see how discovery works with that.What I have encountered is far more intuitive than what I experienced with Vista.If your going for the workgroup type environment, I would suggest the Work network setting.Go from there.I haven't investigated the Homegroup set up yet, but I have gotten further in 4 hours than I did in days of screwing with Vista.Use some patience and read the fine print, all of my moves were made with instructions in the option descriptions.Good Luck!!!!!!!!!!!!

I have had no issues with sharing of network resources in my Windows 7 beta testing. I have several machines running Windows 7, Vista, and XP, one older Windows 2000 server that is still running SQL 2000, that will soon be migrated. I have had my Windows 7 machines part of a Windows 2003 Domain Infrastruture, and Windows 2008 Domain Infrastructure, as well as not part of any domain, and have yet to see any problems with network connectivity between any of the network resources that are properly configured.Shon

i want to share files as easily as i did in XP, that didnt happen with vista, and thanks to the new homegroup screwing things up on W7 its even worse, i could see my shares but didnt have permission to use them, even after setting permissions. so go ahead and say how simple it was, but my clients dont know this stuff and no searching the net is going to help them with IP adresses or permissions.

Whilst I do have some connection issues that seem to be through using WPA2 I have zero problems networking with other PCs in the house.Using nothing but the defaults it installed with I communicate with XP Pro, Vista Ultimate and a SUSE box quite happily and easily.I also forgo the option to set a Homegroup as its pretty much pointless.I can understand that some people may have issues that others don't due to hardware and drivers etc or just from not knowing what they are doing at times, however from my current experience with 7, there is nothing wrong with the actual OS when it comes to this.

lastot069 said:i want to share files as easily as i did in XP, that didnt happen with vista, and thanks to the new homegroup screwing things up on W7 its even worse, i could see my shares but didnt have permission to use them, even after setting permissions. so go ahead and say how simple it was, but my clients dont know this stuff and no searching the net is going to help them with IP adresses or permissions. That's what I meant by "not being able to see" in my original post. One thing I must do is to be able to do is to map multiple network drives off all of the computers on the network. I could get my network places to show me the other computer's names, but no permissions were granted right off the bat. I have decided to go ahead and try again to work through what it will take to get it to work anyways, so as to be able to help my customers when they decide to upgrade to W7 in the future. I still very much like the work Microsoft put into this, a genuine attempt to satisfy everyone that was very disappointed with Vista, and I commend them for that. However, there is a long way to go in the more intricate networking areas. I still stick to my earlier post, that they would easily be able to make it as "click-and-go" as an exclusively XP or 2000 network, so as to why it isn't, who knows? All I can think of is that they want everybody with a desktop and wireless laptop, being the most common home network out there trying to share resources, to have to upgrade to the latest OS every time one is released. I may be wrong, but what else am I supposed to think? Bottom line is that my customers want me in and out of their homes as fast as possible, and having to go through an hour process to do something so simple is not acceptable.

Hitch said:I also forgo the option to set a Homegroup as its pretty much pointless.Good idea Hitch, and thank you. I will try leaving out the Homegroup on this install. However, I must wonder about pre-built systems with this OS already installed and configured before it even leaves the shelf. Guess we'll cross that bridge when we come to it.

Im sure in time someone will find a way to turn all the ____ off by registry values or other, but i would rather see them not implemented at all. my router has built in firewall and my software covers virus and malware. my router also has wireless security so i cant be hacked from outside. so why do i need OS systems i cant turn off?

wow, the forum blanked out c_r_a_p, didnt even know that was a bad word

What I see from the OP and a few others is:a) Putting the cart before the horseb) bad mouthing a beta before you even know all the featuresI was able to do everything you have complained about without changing the setting on my other machines.What you have done is jumped ahead and not read the instructions or feature sets before integrating this OS in your network.Even with the homegroup function turned on, I was able to change the workgroup name and see the rest of my wired and wireless network (WAP2) immediately. My shares all work swimmingly. I mapped a drive to the W7 box with no difficulties, and it still existed after a reboot.I think the OP's problem is he is obsessed with implementing this OS (that is far from production) even though it isn't for sale yet.Riddle me this OP: How many times have used the direct feedback link in the Beta to convey your problems to Micosoft?I had my network running in the time it took you to post your complaints...

BLITZKRIEG1 said:What I see from the OP and a few others is:a) Putting the cart before the horseb) bad mouthing a beta before you even know all the featuresI was able to do everything you have complained about without changing the setting on my other machines.What you have done is jumped ahead and not read the instructions or feature sets before integrating this OS in your network.Even with the homegroup function turned on, I was able to change the workgroup name and see the rest of my wired and wireless network (WAP2) immediately. My shares all work swimmingly. I mapped a drive to the W7 box with no difficulties, and it still existed after a reboot.I think the OP's problem is he is obsessed with implementing this OS (that is far from production) even though it isn't for sale yet.Riddle me this OP: How many times have used the direct feedback link in the Beta to convey your problems to Micosoft?I had my network running in the time it took you to post your complaints... BLITZKRIEG1 looks like a good name for you seeing as how you just come out attacking people here. relax a bit, its not personal!I myself am a certified computer tech and a Damn good network Admin, i think i know a little about what im doing and it didnt work for me. on a few vista machines i had difficulty also, but with tweaking they worked. this didnt work at all even with tweaking. so im glad yours worked for you but i would expect that an option that has worked well since W95 would work in even a beta of W7, and it didnt. its not really a high standard

BLITZKRIEG1 said:I think the OP's problem is he is obsessed with implementing this OS (that is far from production) even though it isn't for sale yet.Since my original post, I have put W7 back on the quad, and have been able to get most of what I want done to work, but my point is that it was not "quick and easy". While it is true those of us that know what we are doing will get it done, most folks out there are not going to have the patience or desire to bully through it. As I said earlier, other than this one area, I like the features, look and feel of W7. I have to be "obsessed" with learning as much as I can with implementing this version as soon as possible, as by the beginning of next year, the majority of computers I'm going to have to work on will have either Vista, W7, or both on them. Since this beta has been made available, I would be foolish to not get a step up on it. And Blitz, I have nothing personal against Microsoft or this OS, I just feel that the networking area has been elevated above the average user's skill level once XP was no longer the flagship OS for personal computers, and it would seem most folks feel the same way.

Well enough of you guys bantering. I have a question. I have Win7Ultimate Beta on Hp-CPQ dx2400 and I connected this PC to the Win 2003 Server domain [ML350 G4] no problem...here it comes BUT my logon script did not run and the only network drive that mapped was my user drive [U:\]. Can anyone tell why my logon script did not run on Win7, but runs no problem on all of my other WinXP stations?